Register an Alchemy Compatibility Package to a User

When you require users of a system to manage their own applications, and those applications have system components (E.g. services), you can register the user components of a Cloudhouse Alchemy Compatibility Package to a specific user post-deployment. You can use the --register command-line option to do so. This option writes all of the Shortcuts and File Associations in the user's context.

Note: Your source Compatibility Package is not modified when it is registered. By default, the user context components are already registered when a package is deployed. If you would like to postpone the registration, use the --noregister command-line argument at the time of deployment.

Prerequisites

To register a Compatibility Package to a user, you need:

  • A system administrator to have previously deployed the system components of a package, such as services and communication modules. This is due to users not having the necessary permissions to perform this deployment.

  • An account with access to the target computer.

  • A valid Licensing Token within the Compatibility Package or user run token store.

Register a Compatibility Package to a User

To register a Compatibility Package to a user:

  1. Start a Command Prompt.

  2. Run the following command: <path_to_package>\Cloudhouse.Container.Deployment.Exe /register

    Where <path_to_package> is the path to the source Compatibility Package you want to register.

    For example: C:\Packages\ERP-v2\Cloudhouse.Container.Deployment.Exe /register.

What Happens During a Registration?

When a Compatibility Package is registered to a user, the following occur:

  1. Any file associations specified in FileAssociations.xml are created in the HKCU registry hive so they are accessible by the current user on the machine.

  2. Any shortcuts specified in Shortcuts.xml are registered for the current user on the machine. Any shortcuts with a path pointing to the All Users Desktop are translated to the Users Desktop and any shortcuts with a path pointing to the All Users Start Menu are translated to the Users Start Menu so they are accessible by the current user on the machine.

Validation

When a Compatibility Package is registered, validations are performed to ensure that:

  • A valid licensing token exists.

  • Shortcuts and File Associations XML files are valid.